build: raise provisioned concurrency to avoid queueing #487
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are cases where order webhooks are sent significantly later than their creations.
This causes potential fillers to receive them late and exclusive fillers may miss their exclusivity period, causing a fade.
Orders are sent 1 at a time, and from the logs it seems that lambda instances can have orders queued, which means we may not have enough of them. This problem is more pronounced when a previous execution of a lambda "hangs" from a ECONN or similar error that makes the notification execution 5+ seconds rather than a quick sub-second operation.